Internet access indication in private lte networks and neutral host networks

ABSTRACT

A Radio Access Network (RAN) element provides an internet indication to a User Equipment (UE) to enable the UE to quickly obtain internet access. The RAN element determines that the RAN element is connected to at least one gateway that provides public internet access, and broadcasts an internet indication. The RAN element determines that the UE has requested public internet access via the RAN element and provides the UE with public internet access.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application in a continuation of U.S. application Ser. No.17/192,293, filed Mar. 4, 2021, which is a continuation of U.S.application Ser. No. 16/540,397, filed Aug. 14, 2019, now U.S. Pat. No.10,986,486, and the entire contents of both are incorporated herein byreference.

TECHNICAL FIELD

The present disclosure relates to private Long Term Evolution (LTE)networks in the Citizens Broadband Radio Service (CBRS) band.

BACKGROUND

The opening of the CBRS band allows private organizations to provideprivate LTE networks. Private LTE networks provide more reliable networkaccess without the interference and congestion inherent in IEEE 802.11(i.e., Wi-Fi) networks. Some organizations may leverage thelightly/semi-licensed bands of the CBRS spectrum to support varioustypes of applications. Typically, to determine the limits of accessprovided by a network connection (e.g., a publicly available Wi-Finetwork), and find an acceptable network with internet access, a userconnects to each network and attempts to access the desired service.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified block diagram of a wireless communication systemconfigured to provide user equipment with information on internetaccessibility, according to an example embodiment.

FIG. 2 is a message flow diagram illustrating a user equipment obtaininginternet access, according to an example embodiment.

FIG. 3 illustrates a user equipment selecting a service provider from aneutral host network, according to an example embodiment.

FIG. 4 is a flowchart illustrating operations of an Evolved Node B (eNB)in providing a user equipment information on internet accessibility,according to an example embodiment.

FIG. 5 is a flowchart illustrating operations of a user equipmentobtaining information about internet access and attaching to a selectedprovider, according to an example embodiment.

FIG. 6 illustrates a simplified block diagram of a device that may beconfigured to perform methods presented herein, according to an exampleembodiment.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

A method is provided to enable an eNB to provide an internet indicationto a UE. The method includes determining that the eNB is connected to atleast one gateway that provides public internet access, and broadcastingan internet indication in a predetermined SIB. The method also includesreceiving an attach request from a UE. The attach request includes anattach type of internet enabled and a PDN type of internet enabled. Themethod further includes forwarding the attach request to an MME.

Example Embodiments

Presented herein are techniques for defining semantics in the attachmentprocedure for CBRS band networks for presenting indicators of services(e.g., internet access) to the user devices before the user deviceattaches to any particular network.

Currently, there are not semantics for the network elements of a privateLTE network to indicate a service (e.g., internet access) is availableto a mobile device. In the absence of such semantic, a mobile device maydiscover a free network and attach to it, only to find out that there isno internet access via the free network. The attach sequence may devolveinto a trial and error method, which can frustrate the end user.Furthermore, this issue may be magnified in Neutral Host Network (NHN)environments, where multiple providers share network elements. Thetechniques presented herein provide for each cell broadcasting thesupport for internet service in the System Information Blocks, such asSystem Information Block 1 (SIB1).

Referring now to FIG. 1 , a wireless communication system 100 is shownthat is configured to enable an Evolved Node B (eNB) to broadcastinternet accessibility within a standard LTE format. The eNB 110includes service advertisement logic 112 that enables the eNB 110 toadvertise internet service accessibility to mobile devices in thevicinity of the eNB 110. The eNB 110 also includes NHN logic 114 thatenables the eNB 110 to act as an access point for multiple serviceproviders (e.g., through multiple gateways).

The wireless communication system 100 also includes a mobile device 120,e.g., a User Equipment (UE), with service logic 125. The service logic125 enables the UE 120 to obtain information from the eNB 110, select aservice provider, and attach to the eNB 110 to obtain internet accessthrough the selected service provider.

The wireless communication system 100 also includes a MobilityManagement Entity (MME) 130 and gateway (GW) devices 140, 142, and 144.The MME 130 is configured to coordinate the data connections for the UE120 as the UE 120 moves between different eNBs. The gateway devices 140,142, and 144 are configured to provide access to Packet Data Network(PDN), which may include internet access. As used herein, each GW device140, 142, and 144 is associated with a different service provider,enabling the eNB 110 to function in a NHN environment with multipleservice providers sharing a network element, i.e., the eNB 110.

In one example, a single operator offers a private LTE cell through eNB110 as a single provider. In other words, the Radio Access Network (RAN)and core network are both owned by a single operator. In this example,the UE 120 may be configured with a service profile with internetservice enabled, and the eNB 110 broadcasts an internet indicationenabled in the SIB1 block. While latching on to the network, the UE 120checks the SIB1 block to determine if the internet indication is beingbroadcast. The UE 120 will attach to the network and configure theattach-type to be internet enabled and the PDN-request-type to beinternet enabled.

On receiving the attach request with the attach-type andPDN-request-type indicating internet enabled, the MME 130 may find thedefault Access Point Name (APN) locally configured. The MME 130 allowsthe UE 120 to attach to the network and facilitate PDN connectivity.Optionally, if the UE 120 has provided an International MobileSubscriber Identifier (IMSI) with the attach request, the MME 130 maydetermine the Public Land Mobile Network (PLMN) for the IMSI anddetermine the default APN for the PLMN. If the UE 120 does not providean IMSI, then a Diffie-Hellman exchange may be used for securityprotection.

Referring now to FIG. 2 , a message flow diagram illustrates messagespassed in the communication system 100 to advertise internetaccessibility to a UE 120. In some instances, a single message depictedin FIG. 2 may represent multiple physical messages between nodes of thecommunication system 100. Initially, the MME 130 configures the eNB 110to provide service to local UEs, such as UE 120, with setup exchange210. In one example, the setup exchange 210 may include a Shared HomeNetwork Identity (SHNI) and a Closed Subscriber Group (CSG) list.Additionally, the UE 120 may be configured (not shown) withauthentication credentials for internet service.

The eNB 110 broadcasts message 215 including a Master Information Block(MIB) and one or more System Information Blocks (SIBs). In one example,the broadcast message 215 includes an internet indication that signalsto local UEs that the eNB can provide internet access. The broadcastmessage 215 may include a Broadcast Control Channel (BCCH) transmissionwith the internet indication in SIB 1. The UE 120 receives the broadcastmessage 215 and detects that the eNB 110 can provide internet access.The UE 120 and the eNB 110 initialize a connection 220 to enable the UE120 to access internet services. In one example, the initialization ofthe connection 220 may include a random access procedure, a RadioResource Control (RRC) connection request from the UE 120, and a RRCconnection response from the eNB 110.

Once the RRC layer between the UE 120 and the eNB 110 is initialized,the UE 120 sends an attach request 230 to the eNB 110. In one example,the attach request 230 may be included in an RRC connection completemessage. Additionally, the attach request 230 may include a PDNconnection request. The eNB 110 forwards the attach request 235 to theMME 130 for handling. The MME 130 detects that the UE 120 is requestinternet service, and may determine a Public Land Mobile Network (PLMN)identity from an IMSI included in the attach request 235.

The Non-Access Stratum (NAS) channel between the UE 120 and the MME 130is secured in exchange 240. In one example, the UE 120 and the MME 130may generate a shared key using a Diffie-Hellman exchange. The sharedkey may then be used to generate pairwise security keys between the UE120 and the MME 130, as well as between the UE 120 and the eNB 110. Thepairwise security keys may be used to secure the NAS channel (i.e.,between the UE 120 and the MME 130) as well as the radio channel (i.e.,between the eNB 110 and the UE 120). The MME 130 establishes a PDNconnection 245 with the service provider GW 140 that will provideinternet access to the UE 120. In one example, the MME determines theAccess Point Name (APN) to establish the PDN link with the GW 140.

The MME 130 sends a context setup request 250 to the eNB 110 to beginthe process for setting up the data connection. In one example, thecontext setup request 250 includes an attach-accept message, a defaultbearer activation request, and a shared key. The eNB 110 sends a message255 to reconfigure the connection between the eNB 110 and the UE 120 forthe data connection. In one example, the message 255 includes theattach-accept message from the MME 130. Based on the message 255 toreconfigure the air interface, the eNB 110 and the UE 120 secure theAccess Stratum (AS) channel 260. Once the AS channel 260 is secured, theeNB 110 sends a context setup response 270 to the MME 130 to indicatethat the eNB 110 is properly configured. The UE 120 sends anattach-complete message 280 to the MME 130 to indicate that the UE 120is attached to the eNB 110 and the UE 120 configured to begin a datasession 290 through the GW 140.

Referring now to FIG. 3 , a system diagram illustrates the UE 120obtaining internet access in an NHN environment with a single operatorof a network element (e.g., eNB 110) offering various services (e.g.,internet access) from multiple service providers (e.g., GW 140, 142, and144). Initially, the service provider gateways 140, 142, and 144 eachprovide information 310, 312, and 314, respectively, to the eNB 110. Theinformation 310, 312, and 314 indicates whether the respective GW 140,142, or 144 is able to provide internet access. The information 310,312, and 314 may also provide indications of the capabilities (e.g.,bandwidth, QoS, congestion, etc.) of each respective GW 140, 142, or144. The NHN logic 114 of the eNB 110 enables the eNB 110 to include alist of service providers that provide internet access in the broadcast320 to the UE 120. In one example, the broadcast 320 includes the MIB,and various SIBs, and the list of service providers is provided in apredetermined SIB, such as SIB17.

The UE 120 receives the broadcast 320 and selects a service providerform among the list of service providers to provide internet access tothe UE 120. The UE 120 responds with an attach request 325 thatspecifies the service provider selected by the UE 120. The eNB 110 setsup the data connection with the selected service provider gateway, andthe UE 120 is able to access the internet through the selected serviceprovider gateway.

In one example, the RAN (e.g., eNB 110) is owned and operated by a CBRSoperator, and multiple providers provide various services (e.g.,internet access) through the RAN. The UE 120 may be configured with aservice profile that indicates internet service is enabled. Optionally,the service profile may indicate a preferred service provider thatoffers internet service. The eNB 110 broadcasts an internet indicationenabled in the SIB1 block. If any of the service providers offerinternet service, the provider would notify the eNB 110, and the eNB 110would enable the internet indication in the SIB1 block. Additionally,the eNB 110 would also broadcast (e.g., in the SIB17 block) whichservice providers are offering internet service.

While latching on to the network, the UE 120 checks the SIB1 block todetermine if the internet indication is being broadcast. If the internetindication is being broadcast, the UE 120 may select a service providerbased on a list of preferred service providers configured in the serviceprofile of the mobile device and based on the service providers listedin the SIB17 block. Optionally, if the UE 120 is not configured with apreferred service provider list, the UE 120 may be presented with a listof service providers from which the UE 120 may select.

The UE 120 with attach to the network and configure the attach-type tobe internet enabled and the PDN-request-type to be internet enabled. TheUE 120 may use a Diffie-Hellman exchange with the network to protect theintegrity and privacy of the security keys. On receiving the attachrequest with the attach-type and PDN-request-type indicating internetenabled, the MME 130 (not shown in FIG. 3 ) will find the default APNlocally configured. The MME 130 allows the UE 120 to attach to thenetwork and facilitate PDN connectivity.

Referring nowt to FIG. 4 , a flowchart illustrating operations performedat an eNB (e.g., eNB 110) in a process 400 for enabling local UEs toobtain internet access efficiently. At 410, the eNB determines that theeNB is connected to at least one gateway that provides public internetaccess. In one example, the eNB may be connected to multiple serviceproviders providing public internet access in a NHN environment. At 420,the eNB broadcasts an internet indication in a predetermined SIB. In oneexample, the internet indication is broadcast as part of SIB1. Inanother example, the eNB may broadcast a list of the service providergateways that provide public internet access in another predeterminedSIB, such as SIB17.

At 430, the eNB receives an attach request from a UE. The attach requestincludes an attach type of internet enabled and a PDN type of internetenabled to indicate that the UE should be connected to a serviceprovider gateway that provides internet access. In one example, theattach request may also include an indication of a specific serviceprovider gateway to connect to the UE for internet access. At 440, theeNB forwards the attach request to a MME, which configures the eNB andUE to connect to a service provider gateway that provides publicinternet access. In one example, the eNB may forward a selection of aparticular service provider gateway to the MME, enabling the MME toconfigure the connection between the UE and the selected gateway.

Referring now to FIG. 5 , a flowchart illustrates operations performedat a UE (e.g., UE 120) in a process 500 to obtain internet accessthrough an eNB. At 510, the UE receives a broadcast including aninternet indication from an eNB. In one example, the internet indicationis included in a predetermined SIB, such as SIB1. At 520, the UEdetermines if there is a list of service provider gateways that providepublic internet access. In one example, the list of service providergateways may be included in another predetermined SIB, such as SIB17. Ifthere is no list of service provider gateways included in the broadcast,then the UE sends an attach request to the eNB at 525.

If the UE did receive a list of service provider gateways in thebroadcast form the eNB, then the UE selects one of the service providersto provide internet access at 530. In one example, the UE may bepreconfigured with a preferred list of service providers that iscompared to the list of service providers broadcast from the eNB toselect a service provider to provide internet access. At 535, the UEsends an attach request to the eNB indicating the service providergateway that is selected to provide internet access.

In response to either the attach request sent at 525 or 535, the UEreceives an attach accept message at 540. The attach accept messageincludes configuration settings for the connection to a service providergateway through the eNB. At 550, the UE configures the connection withthe eNB and the service provider gateway. In one example, the UE and eNBsecure the air interface with a shared key. At 560, the UE begins tosend and receive data to the service provider gateway that providesinternet access to the UE.

Referring now to FIG. 6 , a hardware block diagram illustrates acomputing device 600 that may perform the functions of any of theservers or computing or control entities referred to herein inconnection with the wireless communication system described herein. Itshould be appreciated that FIG. 6 provides only an illustration of oneembodiment and does not imply any limitations with regard to theenvironments in which different embodiments may be implemented. Manymodifications to the depicted environment may be made.

As depicted, the device 600 includes a bus 612, which providescommunications between computer processor(s) 614, memory 616, persistentstorage 618, communications unit 620, and input/output (I/O)interface(s) 622. Bus 612 can be implemented with any architecturedesigned for passing data and/or control information between processors(such as microprocessors, communications and network processors, etc.),system memory, peripheral devices, and any other hardware componentswithin a system. For example, bus 612 can be implemented with one ormore buses.

Memory 616 and persistent storage 618 are computer readable storagemedia. In the depicted embodiment, memory 616 includes random accessmemory (RAM) 624 and cache memory 626. In general, memory 616 caninclude any suitable volatile or non-volatile computer readable storagemedia. Instructions for the service logic 125 or the serviceadvertisement logic 112 may be stored in memory 616 or persistentstorage 618 for execution by processor(s) 614.

One or more programs may be stored in persistent storage 618 forexecution by one or more of the respective computer processors 614 viaone or more memories of memory 616. The persistent storage 618 may be amagnetic hard disk drive, a solid state hard drive, a semiconductorstorage device, read-only memory (ROM), erasable programmable read-onlymemory (EPROM), flash memory, or any other computer readable storagemedia that is capable of storing program instructions or digitalinformation.

The media used by persistent storage 618 may also be removable. Forexample, a removable hard drive may be used for persistent storage 618.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage618.

Communications unit 620, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 620 includes one or more network interface units,such as network interface cards. Communications unit 620 may providecommunications through the use of either or both physical and wirelesscommunications links.

I/O interface(s) 622 allows for input and output of data with otherdevices that may be connected to computer device 600. For example, I/Ointerface 622 may provide a connection to external devices 628 such as akeyboard, keypad, a touch screen, and/or some other suitable inputdevice. External devices 628 can also include portable computer readablestorage media such as database systems, thumb drives, portable opticalor magnetic disks, and memory cards.

Software and data used to practice embodiments can be stored on suchportable computer readable storage media and can be loaded ontopersistent storage 618 via I/O interface(s) 622. I/O interface(s) 622may also connect to a display 630. Display 630 provides a mechanism todisplay data to a user and may be, for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment. However, itshould be appreciated that any particular program nomenclature herein isused merely for convenience, and thus the embodiments should not belimited to use solely in any specific application identified and/orimplied by such nomenclature.

Data relating to operations described herein may be stored within anyconventional or other data structures (e.g., files, arrays, lists,stacks, queues, records, etc.) and may be stored in any desired storageunit (e.g., database, data or other repositories, queue, etc.). The datatransmitted between entities may include any desired format andarrangement, and may include any quantity of any types of fields of anysize to store the data. The definition and data model for any datasetsmay indicate the overall structure in any desired fashion (e.g.,computer-related languages, graphical representation, listing, etc.).

The environment of the present embodiments may include any number ofcomputer or other processing systems (e.g., client or end-user systems,server systems, etc.) and databases or other repositories arranged inany desired fashion, where the present embodiments may be applied to anydesired type of computing environment (e.g., cloud computing,client-server, network computing, mainframe, stand-alone systems, etc.).The computer or other processing systems employed by the presentembodiments may be implemented by any number of any personal or othertype of computer or processing system (e.g., desktop, laptop, PDA,mobile devices, etc.), and may include any commercially availableoperating system and any combination of commercially available andcustom software (e.g., machine learning software, etc.). These systemsmay include any types of monitors and input devices (e.g., keyboard,mouse, voice recognition, etc.) to enter and/or view information.

It is to be understood that the software of the present embodiments maybe implemented in any desired computer language and could be developedby one of ordinary skill in the computer arts based on the functionaldescriptions contained in the specification and flow charts illustratedin the drawings. Further, any references herein of software performingvarious functions generally refer to computer systems or processorsperforming those functions under software control. The computer systemsof the present embodiments may alternatively be implemented by any typeof hardware and/or other processing circuitry.

The various functions of the computer or other processing systems may bedistributed in any manner among any number of software and/or hardwaremodules or units, processing or computer systems and/or circuitry, wherethe computer or processing systems may be disposed locally or remotelyof each other and communicate via any suitable communications medium(e.g., Local Area Network (LAN), Wide Area Network (WAN), Intranet,Internet, hardwire, modem connection, wireless, etc.). For example, thefunctions of the present embodiments may be distributed in any manneramong the various end-user/client and server systems, and/or any otherintermediary processing devices. The software and/or algorithmsdescribed above and illustrated in the flow charts may be modified inany manner that accomplishes the functions described herein. Inaddition, the functions in the flow charts or description may beperformed in any order that accomplishes a desired operation.

The software of the present embodiments may be available on anon-transitory computer useable medium (e.g., magnetic or opticalmediums, magneto-optic mediums, floppy diskettes, CD-ROM, DVD, memorydevices, etc.) of a stationary or portable program product apparatus ordevice for use with stand-alone systems or systems connected by anetwork or other communications medium.

The communication network may be implemented by any number of any typeof communications network (e.g., LAN, WAN, Internet, Intranet, VirtualPrivate Network (VPN), etc.). The computer or other processing systemsof the present embodiments may include any conventional or othercommunications devices to communicate over the network via anyconventional or other protocols. The computer or other processingsystems may utilize any type of connection (e.g., wired, wireless, etc.)for access to the network. Local communication media may be implementedby any suitable communication media (e.g., local area network (LAN),hardwire, wireless link, Intranet, etc.).

The system may employ any number of any conventional or other databases,data stores or storage structures (e.g., files, databases, datastructures, data or other repositories, etc.) to store information(e.g., data relating to user identities or credentials). The databasesystem may be included within or coupled to the server and/or clientsystems. The database systems and/or storage structures may be remotefrom or local to the computer or other processing systems, and may storeany desired data (e.g., data relating to userauthentication/authorization or credentials).

The present embodiments may employ any number of any type of userinterface (e.g., Graphical User Interface (GUI), command-line, prompt,etc.) for obtaining or providing information (e.g., data relating touser authentication/authorization or credentials), where the interfacemay include any information arranged in any fashion. The interface mayinclude any number of any types of input or actuation mechanisms (e.g.,buttons, icons, fields, boxes, links, etc.) disposed at any locations toenter/display information and initiate desired actions via any suitableinput devices (e.g., mouse, keyboard, etc.). The interface screens mayinclude any suitable actuators (e.g., links, tabs, etc.) to navigatebetween the screens in any fashion.

The embodiments presented may be in various forms, such as a system, amethod, and/or a computer program product at any possible technicaldetail level of integration. The computer program product may include acomputer readable storage medium (or media) having computer readableprogram instructions thereon for causing a processor to carry outaspects of presented herein.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

In summary, the techniques presented herein define semantics in theattach procedures for presenting internet support indicators to mobiledevices. The mobile devices do not have to expend time and resources toattach to each network to determine if internet service is available,and can quickly attach to a network that is able to provide internetservice.

In one form, a method is provided to enable an eNB to provide aninternet indication to a UE. The method includes determining that theeNB is connected to at least one gateway that provides public internetaccess, and broadcasting an internet indication in a predetermined SIB.The method also includes receiving an attach request from a UE. Theattach request includes an attach type of internet enabled and a PDNtype of internet enabled. The method further includes forwarding theattach request to an MME.

In another form, an apparatus comprising a network interface, a wirelessinterface, and a processor is provided. The network interface isconfigured to communicate with a plurality of computing devices acrossone or more computer networks. The wireless interface is configured towirelessly communicate with at least one UE. The processor is configuredto determine than an eNB is connected to at least one gateway thatprovides public internet access, and cause the wireless interface tobroadcast an internet indication in a predetermined SIB. The processoris also configured to receive via the wireless interface an attachrequest from the at least one UE. The attach request includes an attachtype of internet enabled and a PDN type of internet enabled. Theprocessor is further configured to cause the network interface toforward the attach request to an MME.

In yet another form a non-transitory computer readable storage media isprovided that is encoded with instructions that, when executed by aprocessor of an eNB, cause the processor to determine that the eNB isconnected to at least one gateway that provides public internet access,and broadcast an internet indication from the eNB in a predeterminedSIB. The instructions also cause the processor receive an attach requestfrom a UE. The attach request includes an attach type of internetenabled and a PDN type of internet enabled. The instructions furthercause the processor to forward the attach request to an MME.

Computer readable program instructions for carrying out operations ofthe present embodiments may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Python, C++, or the like, and procedural programminglanguages, such as the “C” programming language, Python or similarprogramming languages. The computer readable program instructions mayexecute entirely on the user's computer, partly on the user's computer,as a stand-alone software package, partly on the user's computer andpartly on a remote computer or entirely on the remote computer orserver. In the latter scenario, the remote computer may be connected tothe user's computer through any type of network, including a local areanetwork (LAN) or a wide area network (WAN), or the connection may bemade to an external computer (for example, through the Internet using anInternet Service Provider). In some embodiments, electronic circuitryincluding, for example, programmable logic circuitry, field-programmablegate arrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the presented embodiments.

Aspects of the present embodiments are described herein with referenceto flowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to presentedembodiments. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variouspresented embodiments. In this regard, each block in the flowchart orblock diagrams may represent a module, segment, or portion ofinstructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments have been presented forpurposes of illustration, but are not intended to be exhaustive orlimited to the embodiments disclosed. Many modifications and variationswill be apparent to those of ordinary skill in the art without departingfrom the scope and spirit of the described embodiments. The terminologyused herein was chosen to best explain the principles of theembodiments, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A method comprising: at a User Equipment (UE),receiving a broadcast from a Radio Access Network (RAN) element that isconnected to one or more gateways associated with one or morecorresponding service providers, the broadcast including an internetindication indicating that the RAN element is connected to at least onegateway associated with a corresponding service provider that providespublic internet access; sending an attach request to the RAN element toobtain public internet access; receiving an attach accept message fromthe RAN element, the attach accept message including configurationsettings for the UE to connect to a particular gateway among the atleast one gateway associated with a corresponding service provider thatprovides internet access; and configuring a connection between the UEand the RAN element based on the configuration settings.
 2. The methodof claim 1, wherein the broadcast further includes a list of gatewaysassociated with corresponding service providers that provide publicinternet access.
 3. The method of claim 2, further comprising obtaininga selection of the particular gateway from the list of gatewaysassociated with corresponding service providers that provide publicinternet access, wherein the attach request includes an indication ofthe selection of the particular gateway.
 4. The method of claim 1,wherein the internet indication is received in a predeterminedinformation block of the broadcast from the RAN element.
 5. The methodof claim 4, wherein the predetermined information block is a MasterInformation Block (MIB) or a System Information Block (SIB).
 6. Themethod of claim 4, wherein the predetermined information block is SystemInformation Block 1 (SIB1).
 7. The method of claim 4, further comprisingreceiving a list of gateways providing public internet access in anotherpredetermined information block.
 8. An apparatus comprising: a wirelessinterface configured to wirelessly communicate with a Radio AccessNetwork (RAN) element that is connected to one or more gatewaysassociated with one or more corresponding service providers; and aprocessor coupled to the wireless interface, the processor configuredto: receive a broadcast via the wireless interface, the broadcastincluding an internet indication indicating that the RAN element isconnected to at least one gateway associated with a correspondingservice provider that provides public internet access; cause thewireless interface to send an attach request to the RAN element toobtain public internet access; receive an attach accept message from theRAN element via the wireless interface, the attach accept messageincluding configuration settings for the apparatus to connect to aparticular gateway among the at least one gateway associated with acorresponding service provider that provides internet access; andconfigure a connection between the apparatus and the RAN element basedon the configuration settings.
 9. The apparatus of claim 8, wherein thebroadcast further includes a list of gateways associated withcorresponding service providers that provide public internet access. 10.The apparatus of claim 9, wherein the processor is further configured toobtain a selection of the particular gateway from the list of gatewaysassociated with corresponding service providers that provide publicinternet access, wherein the attach request includes an indication ofthe selection of the particular gateway.
 11. The apparatus of claim 8,wherein the wireless interface is configured to receive the internetindication in a predetermined information block of the broadcast fromthe RAN element.
 12. The apparatus of claim 11, wherein thepredetermined information block is a Master Information Block (MIB) or aSystem Information Block (SIB).
 13. The apparatus of claim 11, whereinthe predetermined information block is System Information Block 1(SIB1).
 14. The apparatus of claim 11, wherein the wireless interface isfurther configured to receive a list of gateways providing publicinternet access in another predetermined information block.
 15. One ormore non-transitory computer readable storage media encoded withinstructions that, when executed by a processor of a User Equipment(UE), cause the processor to: receive a broadcast from a Radio AccessNetwork (RAN) element that is connected to one or more gatewaysassociated with one or more corresponding service providers, thebroadcast including an internet indication indicating that the RANelement is connected to at least one gateway associated with acorresponding service provider that provides public internet access;send an attach request to the RAN element to obtain public internetaccess; receive an attach accept message from the RAN element, theattach accept message including configuration settings for the UE toconnect to a particular gateway among the at least one gatewayassociated with a corresponding service provider that provides internetaccess; and configure a connection between the UE and the RAN elementbased on the configuration settings.
 16. The one or more non-transitorycomputer readable storage media of claim 15, wherein the broadcastfurther includes a list of gateways associated with correspondingservice providers that provide public internet access.
 17. The one ormore non-transitory computer readable storage media of claim 16, furthercomprising instructions operable to cause the processor to obtain aselection of the particular gateway from the list of gateways associatedwith corresponding service providers that provide public internetaccess, wherein the attach request includes an indication of theselection of the particular gateway.
 18. The one or more non-transitorycomputer readable storage media of claim 15, wherein the internetindication is received in a predetermined information block of thebroadcast from the RAN element.
 19. The one or more non-transitorycomputer readable storage media of claim 18, wherein the predeterminedinformation block is a Master Information Block (MIB) or a SystemInformation Block (SIB).
 20. The one or more non-transitory computerreadable storage media of claim 18, further comprising instructionsoperable to cause the processor to, receive a list of gateways providingpublic internet access in another predetermined information block.